The tests are failing because we're running into the StressTestTimeout (60s). It's just that without a decent test framework, we don't get a helpful error message.

@marten-seemann it would be really nice to get this passing.

I've updated to the latest test-suite and made the build pass again: https://github.com/liamsi/go-libp2p-quic-transport/tree/transport-test-updated

The tests fail locally but with other fails than StressTestTimeout (60s) (or at least I don't see it if this happens under the hood): https://github.com/liamsi/go-libp2p-quic-transport/runs/3039813604

Edit: Although it seems the SubtestStress1Conn1Stream100Msg is the only one that panics.

@liamsi pulled.

Ok, after libp2p/go-libp2p-testing#34, everything but windows is passing, and windows is failing consistently. This looks like it might be a QUIC bug.

Hm. I take that back? I'm getting:

  stream_suite.go:241: timeout: no recent network activity

On ubuntu as well, but not as reliably.

Also, after a quite a few runs, I'm getting "open sockets", even though I'm cleaning them up. Clearly we're something is failing to garbage collect (could be the test?).

Also, after a quite a few runs, I'm getting "open sockets", even though I'm cleaning them up. Clearly we're something is failing to garbage collect (could be the test?).

Ok, that's just us hanging on to old sessions.

"retired connections"